Method for interacting with user and terminal thereof

ABSTRACT

The present specification related to a method for interacting with a user and terminal thereof. The present specification provides a terminal comprising a first module adapted to receive a scheduling context including scheduled device management from a server and to install the received scheduling context, and a second module adapted to provide one or more of notification to a user about the scheduled device management, and an option allowing the user to modify the scheduled device management before performing the scheduled device management.

RELATED APPLICATION

The present disclosure relates to subject matter contained in priorityApplication No. 60/760,793 filed on Jan. 23, 2006 and priorityApplication No. 60/762,517 filed on Jan. 27, 2006, which are hereinexpressly incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present specification relates to a method for interacting with auser and terminal thereof.

2. Description of the Related Art

In general, a DM technique is a technique that resources of a client(terminal) are shown in the form of a DM object existing on a DM tree toa DM server so that the DM server can access it, thereby allowing the DMserver to easily manage the terminal.

In the DM technique, the DM server may instruct a DM target client toprocess a command for a DM. The DM target client can immediately performthe corresponding command and report the performing result to the DMserver. In addition, the DM server can request the DM client to change,update or delete a particular function.

However, the related art DM technique has shortcomings that a usercannot recognize the performing of the DM.

SUMMARY OF THE INVENTION

One exemplary feature of the present invention is to provide a devicemanagement (DM) system capable of allowing a user to interact withperforming of a DM and a method for interacting with a user in thesystem.

To implement at least the above feature in whole or in parts, thepresent invention provides a terminal comprising a first module adaptedto receive a scheduling context including scheduled device managementfrom a server and to install the received scheduling context; and asecond module adapted to provide one or more of notification to a userabout the scheduled device management, and an option allowing the userto modify the scheduled device management before performing thescheduled device management.

The modification may be at least one of deferring, rescheduling, andcanceling the scheduled device management. The first module can achievethe installation by generating the user interaction node in a DM tree ofa terminal according to the user interaction information of thescheduling context. In this case, the user interaction node can includeone or more of a first node specifying whether to provide to a user amessage about performing of the device management; and a second nodespecifying whether to allow a user to modify the device management.

To implement at least the above feature in whole or in parts, thepresent invention also provides a server comprising a device management(DM) scheduling enabler for generating a scheduling context includingscheduled device management and user interaction information, andrequesting installation of the generated scheduling context in aterminal, wherein the user interaction information includes one of afirst element specifying whether to provide to a user a message aboutperforming of the device management, and a second element specifyingwhether to allow the user to modify the scheduled device management.

To implement at least the above feature in whole or in parts, thepresent invention also provides a method for performing a scheduleddevice management, the method comprises: detecting an arrival onschedule for performing a device management; providing at least one of anotification to a user, and an option allowing the user to change theschedule; performing the device management.

Additional advantages, objects, and features of the invention will beset forth in part in the description which follows and in part willbecome apparent to those having ordinary skill in the art uponexamination of the following or may be learned from practice of theinvention. The objects and advantages of the invention may be realizedand attained as particularly pointed out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be described in detail with reference to thefollowing drawings in which like reference numerals refer to likeelements wherein:

FIG. 1 is a view showing the structure of a device management (DM)system according to an exemplary embodiment of the present invention;

FIG. 2 is a view showing a scheduling context in the form of a DM tree;

FIG. 3 is a flow chart showing a process of installing the schedulingcontext by a DM server in FIG. 1; and

FIG. 4 is a flow chart showing a schedule componenting method.

DETAILED DESCRIPTION OF THE INVENTION

A device management (DM) system and a method for interacting with a userin the system according to the exemplary embodiment of the presentinvention will now be described with reference to the accompanyingdrawings.

FIG. 1 is a view showing the structure of a device management (DM)system according to an exemplary embodiment of the present invention,and FIG. 2 is a view showing a scheduling context in the form of a DMtree.

As shown in FIG. 1, the DM system according to the present inventionincludes a DM server 100 and a terminal 200.

DM Sever 100

The DM server 100 includes a DM scheduling enabler 110 and a DM enabler120.

The DM scheduling enabler 110 can create a scheduling context andrequest the terminal 200 to install the created scheduling context so asto be performed therein.

In detail, the DM scheduling enabler 110 may create a scheduling contextincluding general information and a schedule component. The generalinformation may include an identifier of the scheduling context, thename of the scheduling context, a valid period of the schedulingcontext, and a server for owning the scheduling context, and apermission given to a user.

The schedule component may include scheduled device management and userinteraction information. The scheduled device management may include aDM command and a condition for executing the DM command. The userinteraction information may include one of a first element specifyingwhether to provide to a user a message about executing of the devicemanagement, and a second element specifying whether to allow the user tomodify the scheduled device management. Here, the second elementcomprises one or more of a defer element specifying whether to allow auser to defer the device management, and a reschedule element specifyingwhether to allow the user to re-schedule the device management. In thiscase, the user interaction information may further include an elementspecifying whether to allow the user to confirm or cancel performing ofthe device management.

The DM scheduling enabler 110 may establish a session according to anOMA DM specification together with the terminal 200 and request theterminal 200 to install the generated scheduling context through theestablished session.

The DM enabler 120 performs a non-scheduled DM in cooperation with theDM enabler of the terminal.

Terminal 200

The terminal 200 may include a DM scheduling enabling unit 210 and a DMenabler 220.

The DM scheduling enabler 210 may include a scheduling contextinstallation module 211, a conditions matching module 212 for checkingwhether a condition of executing a DM command is matched or not, a userinteraction module 213, and a DM command executing module 214.

The scheduling context installation module 211 receives a request forinstalling a scheduling context from the DM server 100 and processes it.Namely, when the scheduling context installation module 211 receives therequest from the server 100, it installs the scheduling context in theform of a DM tree within the terminal 200. In this case, the DM tree mayinclude a general part and one or more schedule components.

The DM tree, the form of installation of the scheduling context, will bedescribed as follows. The DM tree can have the structure as shown inFIG. 2.

In detail, as shown in FIG. 2, the general part includes an Id nodeindicating an identifier of the installed scheduling context, a Namenode indicating a name of the scheduling context, a Valid nodeindicating a valid period of the scheduling context, a Server nodeindicating an owner of the scheduling context, and a User Control nodespecifying a permission given to a user.

The schedule component may include a Task node specifying a DM command(or, a message which includes at least one or more DM commands), aCondition node specifying a condition for executing the DM command, anda UI (User Interaction) node specifying a user interaction.

The UI node may include a Msg (Message) node specifying whether toprovide to a user a message about executing of the scheduled devicemanagement, and a Modify node specifying whether to allow the user tomodify the scheduled device management. The Msg node may include aMinimum duration time node specifying a minimum time that the message isto be provided to the user, and a maximum duration time node specifyinga maximum time that the message is to be provided to the user. And, theModify node comprises one or more of a Defer node specifying whether toallow the user to defer the scheduled device management, a Reschedulenode specifying whether to allow the user to re-schedule the scheduleddevice management and a Cancel node specifying whether to allow the userto cancel the scheduled device management. The UI node may furtherinclude a Deadline node specifying a deadline deferred or re-scheduledby the user when deferring or rescheduling can be possible.

The scheduling context installation module 211 can interact with theuser, before the scheduling context is installed. The interaction mayinclude a provision of a notification about the installation of thescheduling context to the user. In addition, the interaction may includea provision of an option allowing the user to confirm or cancel theinstallation of the scheduling context. Also, the interaction mayinclude a provision of an option allowing the user to view, changesuspend or terminate the scheduled device management.

The conditions matching module 212 monitors whether the condition ismatched or not, and when the condition is matched, the conditionsmatching module 212 requests user interaction to the user interactionmodule 213 or requests the DM command executing module 214 to executethe DM command corresponding to the conditions.

The user interaction module 213 performs the user interaction when theconditions matching module 212 determines that the condition is matched.

The user interaction module 213 can provide a message to the user aboutthe scheduled device management, i.e. the DM command and the condition.

Also, the user interaction module 213 can provide an option and receivea response corresponding to the option from the user. In detail, theuser interaction module 213 may provide an option allowing the user toview and change the scheduled device management according to the Modifynode. Namely, the user interaction module 213 may provide one or more ofan option allowing the user to defer the scheduled device managementaccording to the Defer node in the DM tree, and an option allowing theuser to reschedule the scheduled device management, according to theReschedule node of the DM tree (refer to Table 1 shown below).

Also, the user interaction module 213 may provide an option allowing theuser to confirm or cancel executing of the scheduled device management.

In addition, the user interaction module 213 may provide an optionallowing the user to stop or start operation of the scheduling contextor suspend or resume the operation of the scheduling context as in table2 shown below.

TABLE 1 Type of user interaction Description Message Providing a messageabout scheduling context or DM command Defer Deferring of scheduled DMcommand Reschedule Re-scheduling DM

TABLE 2 Type of user interaction Description Stop and start Stopping orstarting operation of scheduling context Suspend and Suspending orresuming operation of scheduling context resume

As afore-mentioned, if the user changes the scheduled device management,the user interaction module 213 may allow the DM scheduling enabler 110of the server 100 to recognize the change.

The DM command executing module 214 cooperates with the DM enabler 110to perform the DM command, when the conditions matching module 212determines that the condition is matched, and the user interaction iscompleted.

The DM enabler 220 performs the DM command in cooperation with the DMcommand executing module 214. In detail, the DM enabler 220 receives theDM command from the DM command executing module 214 and executes it, andthen, returns a result to the DM command executing module 214.

In the construction of the DM system according to the present invention,the DM server 100 includes the DM scheduling enabler 110 and the DMenabler 120, and the terminal 200 includes the DM scheduling enabler 210that includes the scheduling context installation module 211, theconditions matching module 212, the user interaction module 213 and theDM command executing module 214, and the DM enabler 220. However, the DMserver 100 and the terminal 200 may include a processor (not shown), anetwork interface (not shown) and a storage unit (not shown).

The operation of the DM system constructed as described above will nowbe explained in detail with reference to FIGS. 3 and 4. In FIGS. 3 and4, some elements are omitted for the sake of brevity, but the operationon the drawing is definitely performed by all the elements of the DMserver 100 and the terminal 200.

FIG. 3 is a flow chart showing a process of installing the schedulingcontext by the DM server 100 in FIG. 1.

The installing process will be described as follows.

1) First, the DM server 100 (specifically, the DM scheduling enabler110) creates the scheduling context including the general informationand the schedule component. In this case, as mentioned above, theschedule component may include the DM command, the conditions forexecuting the DM command, and the user interaction information, etc.

2) Next, the DM server 100 connects a session to the DM schedulingenabler 210 of the terminal 200 and transfers an installation request ofthe generated scheduling context by using a DM protocol.

3) Then, the DM scheduling enabler 210 (specifically, the schedulingcontext installation, module 211) of the terminal 200 selectively makesthe user confirm the installation of the scheduling context.

4) When the user interaction is completed, the DM scheduling enabler 210(specifically, the scheduling context installation module 211) of theterminal 200 installs the scheduling context in the form of the DM treewithin the terminal 200.

5) When the installing is completed, the DM scheduling enabler 210 ofthe terminal reports a result of installation of the scheduling contextto the DM server 100.

FIG. 4 is a flow chart showing the DM scheduling method according to theexemplary embodiment of the present invention.

Each process will be described with reference to FIG. 4 as follows.

1) First, the DM scheduling enabler 210 (specifically, the conditionsmatching module 212) checks the Condition node of the DM tree to monitorwhether a condition for executing a DM command is matched.

2) When the condition is checked to be matched according to themonitoring, the DM scheduling enabler 210 (specifically, the userinteraction module 213) selectively performs user interaction. Herein,the user interaction can be performed according to the UI node of the DMtree as mentioned above.

In detail, the user interaction module 213 may provide to the user amessage about information on the scheduling context or the informationon the DM command according to the Notify node.

Also, the user interaction module 213 may provide one or more of anoption allowing the user to modify the scheduled device management. Indetail, the user interaction module 213 may allow the user to defer theschedule according to the Defer node, or allow the user to reschedulethe schedule according to the Reschedule node.

In addition, the user interaction module 213 may provide an optionallowing the user to stop or start the operation of the schedulingcontext or suspend or resume the operation of the scheduling context.Also, the user interaction module 213 may provide an option allowing theuser to confirm or cancel executing of the DM command. Also, the userinteraction module 213 may provide an option allowing the user to viewor change the schedule.

3) When the user interaction is successfully performed, the DMscheduling enabler 210 (specifically, the DM command executing module214) performs the DM command in cooperation with the DM enabler 220.

The method according to the present invention as described above can beimplemented by software, hardware, or their combination. For example,the method according to the present invention can be implemented withcodes or command languages in a software program that can be stored in astorage medium (e.g., an internal memory of a mobile terminal, a flashmemory, a hard disk, or something else) and executed by a processor(e.g., an internal microprocessor of the mobile terminal).

As so far described, the DM system and a method for interacting with auser in the system according to the present invention have the followingadvantages.

That is, when the DM is performed, the user can interact therewith.

In addition, the user can arbitrarily change performing of the DM.

Also, the DM server can provide an improved DM by interacting with theuser.

The foregoing embodiments and advantages are merely exemplary and arenot to be construed as limiting the present invention. The presentteaching can be readily applied to other types of apparatuses. Thedescription of the present invention is intended to be illustrative, andnot to limit the scope of the claims. Many alternatives, modifications,and variations will be apparent to those skilled in the art. In theclaims, means-plus-function clauses are intended to cover the structuredescribed herein as performing the recited function and not onlystructural equivalents but also equivalent structures.

1. A device management (DM) method of a terminal, comprising: receiving,by the terminal, a schedule from a server; installing the receivedschedule in a form of a device management tree, wherein the installedschedule includes a task including a command for device management, acondition for execution of the task, and user interaction information,wherein the user interaction information includes at least one of afirst element relating to a confirmation of the execution of the task, asecond element specifying whether it is possible to reschedule theexecution of the task, and a deadline element specifying a deadlineuntil which it is possible to defer or reschedule the execution of thetask, and wherein the schedule further includes control information;providing, based on the control information, a first function capable ofstopping or starting an operation of the schedule; providing, based onat least one of the first element, the second element and the deadlineelement, a second function capable of confirming or rescheduling theexecution of the task when a state of the schedule is changed into beingstarted; and executing the task by the terminal without connecting withthe server if the condition is satisfied.
 2. The method of claim 1,wherein states of the schedule comprise: a running state indicating thatan operation of the schedule is started; and a stopped state indicatingthat the operation of the schedule is stopped.
 3. The method of claim 1,wherein the second function is adapted to be capable of deferring orcanceling the execution of the task.
 4. The method of claim 1, whereinthe user interaction information further comprises: a defer elementadapted to be capable of deferring the execution of the task.
 5. Themethod of claim 1, further comprising: providing, by the terminal, oneor more notifications about the installation of the schedule; andproviding, by the terminal, a third function capable of canceling theinstallation of the schedule.
 6. The method of claim 1, furthercomprising: providing, by the terminal, a fourth function capable ofviewing, changing, suspending or terminating the schedule.
 7. The methodof claim 1, wherein the first function is further adapted to be capableof stopping, starting, suspending or resuming the operation of theschedule.
 8. A device management (DM) method of a terminal, comprising:receiving, by the terminal, a schedule from a server; installing, thereceived schedule by generating objects into a device management tree,wherein the installed schedule includes a task that contains a commandfor device management, a condition for execution of the task, and userinteraction information, wherein the user interaction informationincludes at least one of a first element relating to a confirmation ofthe execution of the task, a second element specifying whether it ispossible to reschedule the execution of the task and a deadline elementspecifying a deadline until which it is possible to defer or reschedulethe execution of the task, and wherein the schedule includes valid timeinformation specifying a valid period and server information specifyingan owner of the schedule; providing, based on at least one of the firstelement, the second element and the deadline element, a first functioncapable of confirming or rescheduling the execution of the task; andexecuting the task by the terminal without connecting with the server ifthe condition is satisfied when the schedule is valid based on the validtime information.
 9. The method of claim 8, wherein the first functionis further adapted to be capable of deferring or canceling the executionof the task.
 10. The method of claim 8, wherein the user interactioninformation further comprises: a defer element adapted to be capabledeferring the execution of the task.
 11. The method of claim 8, furthercomprising: providing, by the terminal, one or more notifications aboutthe installation of the schedule; and providing, by the terminal, athird function capable of canceling the installation of the schedule.12. The method of claim 8, further comprising: providing, by theterminal to the user, a fourth function capable of viewing, changing,suspending or terminating the schedule.
 13. The method of claim 8,wherein the first function is further adapted to be capable of stopping,starting, suspending or resuming the operation of the schedule.